Systems and techniques for non-volatile memory buffering

ABSTRACT

An apparatus, system, method, and article for non-volatile memory buffering are described. The apparatus may include a data storage manager to store a data item in a rewritable non-volatile memory buffer. The data item may have a file size less than or equal to a threshold value. The rewritable non-volatile memory buffer may include one or more rewritable memory regions configured to store the data item. Other embodiments are described and claimed.

BACKGROUND

The performance requirements of the wireless device industry continue toincrease as wireless telephones and handheld devices adopt colorscreens, cameras, Web browsing, video, and music capabilities asstandard features. Rapid adoption of these features demands memorysystems with better performance, price, and power consumptionrequirements.

Conventional methods for handling data files in non-volatile memory mayresult in inefficient utilization, excessive operations causing poorthroughput efficiency, and data loss. For example, requiring data filesto be written in full storage region granularity may be inefficient forsmall data files and utilize a large amount of non-volatile memory.Reclaiming free space from utilized non-volatile memory may requireexcessive erase operations resulting in performance degradation. Inaddition, buffering small data in random-access memory (RAM) may beprone to data loss from power-off or hangs. Therefore, there is a needfor non-volatile memory systems and techniques to improve data storageefficiency and performance.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates one embodiment of a memory system.

FIG. 2 illustrates one embodiment of a memory.

FIG. 3 illustrates one embodiment of a memory.

FIG. 4 illustrates one embodiment of a data storage manager

FIG. 5 illustrates one embodiment of a logic flow.

DETAILED DESCRIPTION

Various embodiments are directed to systems and techniques fornon-volatile memory buffering. In one embodiment, a small data itemhaving a file size less than or equal to a threshold value may be storedin a non-volatile memory buffer. The non-volatile memory buffer maycomprise a rewritable non-volatile memory buffer including one or morerewritable memory regions configured to store one or more small dataitems. When the non-volatile memory buffer reaches or nears data storagecapacity, the non-volatile memory buffer may be marked to reclaim freespace, and the one or more small data items stored in the non-volatilememory buffer may be moved to a separate or more permanent storagelocation. In various implementations, the non-volatile memory bufferingsystems and techniques potentially may result in improved memoryutilization, a reduced number of required reclaim operations, and datapreservation.

FIG. 1 illustrates one embodiment of a memory system 100. The memorysystem 100 generally may comprise various physical or logical entitiesfor receiving and storing information and may be implemented ashardware, software, or any combination thereof, as desired for a givenset of design parameters or performance constraints.

In various embodiments, the memory system 100 may comprise or beimplemented by a wireless device such as a mobile telephone, handheldcomputer, personal digital assistant (PDA), combination mobiletelephone/PDA, data transmission device, handset, one-way pager, two-waypager, a wireless access point, a base station (BS), a subscriberstation (SS), a mobile subscriber center (MSC), a radio networkcontroller (RNC), and so forth. When implemented as a wireless device,the memory system 100 may include components and interfaces for wirelesscommunication, such as one or more antennas, transmitters, receivers,transceivers, amplifiers, filters, control logic, and so forth.

Although some embodiments may be described with memory system 100implemented as a wireless device by way of example, it may beappreciated that the embodiments are not limited in this context. Forexample, in some embodiments, the memory system 100 may comprise, or beimplemented as a personal computer (PC), a laptop, a digital musicplayer, a computer system or sub-system, an appliance, a workstation, aterminal, a server, a set top box (STB), a microprocessor, an integratedcircuit such as an application specific integrated circuit (ASIC), aprogrammable logic device (PLD), a processor such as general purposeprocessor, a digital signal processor (DSP) and/or a network processor,an interface, an input/output (I/O) device (e.g., keyboard, mouse,display, printer), a router, a hub, a gateway, a bridge, a switch, acircuit, a logic gate, a register, a semiconductor device, a chipset, achip, die, or other device, machine, tool, equipment, component, orcombination thereof.

As shown, the memory system 100 may comprise a data storage manager 102.In various embodiments, the data storage manager 102 may comprise or beimplemented by software, a software module, an application, a program, asubroutine, an instruction set, computing code, words, values, symbolsor combination thereof. In various implementations, the data storagemanager 102 may be integrated with an operating system (OS) of a device,such as a real-time operating system (RTOS) for use in real-timeembedded applications.

In various embodiments, the data storage manager 102 may be arranged toreceive information over one more communications media 104.Communications media 104 generally may comprise any medium capable ofcarrying information signals. For example, communication media 104 maycomprise wired communication media, wireless communication media, or acombination of both, as desired for a given implementation. Examples ofwired communications media may include a wire, cable, printed circuitboard (PCB), backplane, switch fabric, semiconductor material,twisted-pair wire, co-axial cable, fiber optics, and so forth. Anexample of a wireless communication media may include portions of awireless spectrum, such as the radio-frequency (RF) spectrum. Theembodiments are not limited in this context.

The data storage manager 102 may be arranged to receive one or moretypes of information, such as media information and control information.Media information generally may refer to any data representing contentmeant for a user, such as image information (e.g., digital photographs,user interfaces, Web pages, graphics), audio information (e.g., music,sounds, ring tones), video information (e.g., video files, video clips,movies, broadcast programming), audio/video (A/V) information, voiceinformation, textual information (e.g., e-mail messages, text messages,instant messages, contact lists, task lists, calendar entries,hyperlinks), numerical information, alphanumeric symbols, charactersymbols, and so forth. Control information generally may refer to anydata representing commands, instructions or control words meant for anautomated system. For example, control information may be used to routemedia information through a system or to process the media informationin a certain manner. The embodiments are not limited in this context.

In various embodiments, the information delivered to the data storagemanager 102 may comprise a data item 106. The data item 106 maycomprise, for example, a data file or data packet having a sizerepresented in terms of bits or bytes. In various implementations, mediainformation and control information delivered to the data storagemanager 102 may be segmented into a series of data packets. A datapacket generally may comprise a discrete data set having a fixed orvarying size. Each data packet may contain a portion of the mediainformation plus some control information and have a sequence number.The control information may assist routing each data packet to anintended destination. A set of data packets may be placed in the correctorder using the sequence numbers to reproduce the media information. Itcan be appreciated that the described embodiments are applicable to anytype of communication content or format, such as data packets, datafiles, cells, frames, fragments, units, and so forth.

In various implementations, the data storage manager 102 may be arrangedto store the data item 106 in memory 108. The memory 108 generally maybe implemented as one or more types of computer-readable storage mediacapable of storing data, including both volatile and non-volatilememory. For example, memory 108 may include read-only memory (ROM),random-access memory (RAM), dynamic RAM (DRAM), Double-Data-Rate DRAM(DDRAM), synchronous DRAM (SDRAM), static RAM (SRAM), programmable ROM(PROM), erasable programmable ROM (EPROM), electrically erasableprogrammable ROM (EEPROM), flash memory, content addressable memory(CAM), polymer memory (e.g., ferroelectric polymer memory), phase-changememory (e.g., ovonic memory), ferroelectric memory,silicon-oxide-nitride-oxide-silicon (SONOS) memory, disk memory (e.g.,floppy disk, hard drive, optical disk, magnetic disk), or card (e.g.,magnetic card, optical card), or any other type of media suitable forstoring information.

In various embodiments, the memory 108 may comprise a non-volatilememory, such as NOR or NAND flash memory, or any other type ofnon-volatile memory, such as polymer or ferroelectric memory. Examplesof flash memory include, for example, Intel® Flash Memory products, suchas StrataFlash® Cellular Memory and Intel® Wireless Flash Memory, andother types of flash memory. In general, flash memory may be used tostore both static and dynamic information. Static information maycomprise any information stored in flash memory that may not be altered,changed or updated. Examples of static information include read-onlydata and read-only code. Dynamic information may comprise anyinformation stored in flash memory that may be altered, changed, and/orupdated. Examples of dynamic information include read/write data andread/write code. The embodiments are not limited in this context.

In various embodiments, the data storage manager 102 may be arranged tostore the data item 106 in memory 108, such as in flash memory (e.g.,NOR or NAND flash memory). In various implementations, the data item 106may comprise media information to be stored in flash memory, such asmedia files and/or data files that are required to be immediatelystored, instantly transmitted, updated and/or edited. In suchimplementations, the data storage manager 102 may be arranged to manageand store the media files and/or data files in the flash memory.Examples of media files to be stored in flash memory include: imagefiles (e.g., digital photographs), audio files (e.g., music files, soundfiles), and so forth that might require editing. Examples of data filesto be stored in flash memory include: system files, text messaging,e-mail messages, contact lists, task lists, calendar entries, and soforth that might require immediate storage and/or frequent updating(e.g., addition of new data, deletion of obsolete data). The embodimentsare not limited in this context.

As shown, the memory 108 may comprise a non-volatile memory buffer 110.The non-volatile memory buffer 110 may be implemented, for example, bynon-volatile memory, such as NOR or NAND flash memory. In variousembodiments, the non-volatile memory buffer 110 may be configured to berewritable, and the data storage manager 102 may be arranged to performbuffering of small data items in the non-volatile memory buffer 110. Invarious implementations, a small data item may comprise a data item 106having a file size less than or equal to a threshold value.

In various embodiments, the data storage manager 102 may be arranged todetermine the file size of the data item 106 and compare the file sizeto the threshold value. The threshold value generally may be used todetermine if file size of the data item 106 fits a target size forstorage in the non-volatile memory buffer 110. In some cases, thethreshold value may be a predefined and/or set value. In other cases,the threshold may be a floating and/or configurable value. In variousimplementations, the threshold value may comprise or be based on a datastorage capacity (e.g., 512 bytes) of the non-volatile memory buffer110.

In various embodiments, the data storage manager 102 may be arranged tostore the data item 106 in memory 108 based on the file size of the dataitem 106. For example, if the data item 106 comprises a file sizegreater than the threshold value, the data storage manager 102 may bearranged to perform standard file handling and write processing.Standard file handling and write processing may comprise, for example,storing the data item 106 in a write-restricted memory region of flashmemory.

In various embodiments, the data storage manager 102 may be arranged tostore the data item 106 in the non-volatile memory buffer 110 if thedata item 106 comprises a small data item having a file size less thanor equal to the threshold value. In some cases, the file size of thedata item 106 may be less than the threshold value. For example, thefile size of a data item 106 may comprise only 32 bytes or 64 bytes,while the threshold value may comprise 512 bytes.

In various embodiments, if the file size of the data item 106 is lessthan or equal to the threshold value, the data storage manager 102 maybe arranged to determine whether a non-volatile buffer 110 exists ormust be allocated. In various implementations, the data storage manager102 may be arranged to allocate the non-volatile memory buffer 110. Insome cases, the memory buffer 110 may be allocated on-the-fly and maycomprise floating memory regions in memory 108. In other cases, thenon-volatile memory buffer 110 may be pre-allocated within the memory108.

As shown, the non-volatile memory buffer 110 may comprise one or morenon-volatile memory regions, such as non-volatile memory region 112-1and non-volatile memory region 112-2. In various embodiments, anon-volatile memory region may comprise the smallest write structuresupported by the non-volatile memory. In various implementations, thedata storage manager 102 may allocate the non-volatile memory buffer 110by programming the non-volatile memory regions 112-1, 112-2 innon-volatile memory. Although a limited number of non-volatile memoryregions are shown by way of example, it can be appreciated that more orfewer non-volatile memory regions may be used for a givenimplementation.

In various embodiments, the non-volatile memory regions 112-1, 112-2 maybe programmed in one or more modes. In one embodiment, for example, thenon-volatile memory regions 112-1, 112-2 may be configured forprogramming in an object mode or a control mode. Object mode programminggenerally may be used for storing static information, such as objects orpayloads that rarely change. Control mode programming generally may beuseful for storing dynamic information, such as header information andfile information.

In various implementations, the full data storage capacity of an objectmode non-volatile memory region may be available for data storage. Forexample, object mode programming may allow up to a full 1 KB of data tobe programmed in bits, bytes, or words into a 1 KB non-volatile memoryregion. Multiple object mode non-volatile memory regions may be used tostore more than 1 KB of data.

In object mode programming, however, multiple programming operations maybe not supported. For example, an object mode non-volatile memory regionmay not be augmented or over-written without first erasing the entirememory block containing the non-volatile memory region. An object modememory region may be referred to as one-time write or write-restrictedmemory region.

In various implementations, less than the full capacity of a controlmode non-volatile memory region may be available for data storage. Forexample, only a portion (e.g., half) of a control mode non-volatilememory region may be programmed, while the rest of the control modenon-volatile memory region may remain erased and unusable. In oneexample, control mode programming may allow up to 512 KB of data to beprogrammed in bits, bytes, or words into a 1 KB non-volatile memoryregion.

In contrast to object mode programming, however, control modeprogramming may support multiple programming operations. As such, acontrol mode non-volatile memory region may be rewritable and supportmultiple operations for writing, rewriting, over-writing, augmenting,altering, changing, and/or updating dynamic information.

In various embodiments, the non-volatile memory buffer 110 may comprisea rewritable non-volatile memory buffer including one or more rewritablenon-volatile memory regions. In one embodiment, for example, therewritable non-volatile memory buffer 110 may comprise a firstnon-volatile memory region 112-1 and a second non-volatile memory region112-2. In this embodiment, each of the non-volatile memory regions112-1, 112-2 may be configured to be rewritable and to support multipleprogramming operations for storing one or more small data items. Each ofthe non-volatile memory regions 112-1, 112-2 may be configured to have adata storage capacity comprising only a portion (e.g., half) of a fulldata storage capacity for a non-volatile memory region. In variousimplementations, the data storage manager 102 may be arranged to store adata item 106 having a file size less than or equal to the thresholdvalue in the first non-volatile memory region 112-1 or in the secondnon-volatile memory region 112-2.

In various implementations, the non-volatile memory regions 112-1, 112-2may be configured using control mode programming. In one example, eachof the non-volatile memory regions 112-1, 112-2 may comprise a 1 KBmemory region, with a data storage capacity comprising 512 bytes andwith 512 bytes remaining erased and unusable. In this example, it can beappreciated the cumulative data storage capacity of the firstnon-volatile memory region 112-1 and the second non-volatile memoryregion 112-2 may comprise the full data storage capacity of anon-volatile memory region, such as an object mode programming region.

In various implementations, the data storage manager 102 may determinewhether the file size of the data item 106 is less than or equal to freespace in the non-volatile memory buffer 110. The free space in thenon-volatile memory buffer 110 may comprise, for example, the availablestorage capacity of the first non-volatile memory region 112-1 and/orthe available storage capacity of the second non-volatile memory region112-2.

In various embodiments, if the file size of the data item 106 is greaterthan the free space in the non-volatile memory buffer 110, the datastorage manager 102 may mark or initiate a process on the non-volatilememory 110 for reclaim and may allocate one or more additionalnon-volatile memory regions to be used for non-volatile buffering. Theadditional allocated non-volatile memory regions may comprise, forexample, an annex to the non-volatile memory buffer 110 and/or a newnon-volatile memory buffer. Marking the non-volatile memory buffer 110for reclaim may result in subsequent operations to retrieve free spacefrom dirty space. Reclaim operations may comprise, for example, copyingor moving the data stored in the non-volatile memory buffer 110 to aseparate memory location and then erasing the non-volatile memory buffer110 to reclaim free space. The reclaim operations may be triggered whenthe amount of dirty space exceeds a certain amount of the non-volatilememory buffer (background reclaim) and/or when one or more additionalmemory regions are allocated (foreground reclaim).

In various embodiments, the data storage manager 102 may be arranged towrite the data item 106 to the non-volatile memory buffer 110 if thefile size of the data item 106 is less than or equal to the availablefree space in the non-volatile memory buffer 110. Writing the data item106 to the non-volatile memory buffer 110 may comprise, for example,writing, rewriting, augmenting, altering, changing, and/or updating thememory buffer 110. In various implementations, the data item 106 may bewritten to a rewritable non-volatile memory region of the memory buffer110, such as to the first non-volatile memory region 112-1 or to thesecond non-volatile memory region 112-2, for example.

In various embodiments, the memory 108 may comprise an allocation table114. The allocation table 114 may comprise, for example, a datastructure for storing header information pointing to locations in thenon-volatile memory buffer 110. As shown in FIG. 1, the non-volatilememory buffer 110 may comprise data files (Data1 . . . Data8), and theheader information may point to the locations of the data files (Data1 .. . Data8) stored in the non-volatile memory buffer 110. In variousimplementations, the data storage manager 102 may be arranged to writeand/or update the allocation table 114 in response to storing the datafiles (Data1 . . . Data8) in the non-volatile memory buffer 110. Thedata files (Data1 . . . Data8) may comprise small data items having anaggregate size of less than or equal to the storage capacity (e.g., 1KB) of the non-volatile memory buffer 110, such as eight 128 byte smalldata items, for example.

In various embodiments, the allocation table 114 may comprise arewritable non-volatile memory region configured to support storingdynamic header information. The header information stored in theallocation table 114 may require updating, for example, if the pointerschange. The rewritable non-volatile memory region may be configured tohave a data storage capacity comprising a portion (e.g., half) of a fulldata storage capacity for a non-volatile memory region. In variousimplementations, the rewritable non-volatile memory region may beconfigured using control mode programming, for example. In one example,the rewritable non-volatile memory region may comprise a 1 KB memoryregion, with a data storage capacity comprising 512 bytes and with 512bytes remaining erased and unusable.

In various embodiments, the data storage manager 102 may be arranged todetermine whether the non-volatile memory buffer 110 has reached or isnearing a data storage capacity. In various implementations, the datastorage manager 102 may determine if a certain data capacity thresholdof the memory buffer 110 has been met. The determination may be made,for example, after the data storage manager 102 has stored the data item106 in the non-volatile memory buffer 110. If the data capacitythreshold of the non-volatile memory buffer 110 has been met, the datastorage manager 102 may be arranged to mark or initiate a process on thenon-volatile memory 110 for reclaim. Otherwise, the data storage manager102 potentially may store one or more additional small data items in thenon-volatile memory buffer 110.

In various embodiments, the data storage manager 102 may be arranged tomove the contents of the non-volatile memory buffer 110 to a separate ormore permanent memory location. In various implementations, the datastorage manager 102 may copy the contents of the non-volatile memorybuffer 110 to the separate memory location after the data capacitythreshold of the non-volatile memory buffer 110 has been met and/or thenon-volatile memory 110 has been marked for reclaim. In suchimplementations, moving and/or copying the content of the non-volatilememory buffer 110 may comprise a write complete operation. The contentsof the non-volatile memory buffer 110 may comprise, for example, one ormore small data items.

In one embodiment, the separate memory location may comprise awrite-restricted non-volatile memory region, such as an object modememory region, such as an object mode memory region. For example, thecontents of a 1 KB non-volatile memory buffer 110 comprising rewritablenon-volatile memory regions 112-1, 112-2 (e.g., control modenon-volatile memory regions) may be copied to a single 1 KBwrite-restricted non-volatile memory region (e.g., object mode memoryregion). In this example, it can be appreciated that the contents of thenon-volatile memory buffer 110 may be written to the separate memorylocation in full storage region granularity.

In various implementations, the memory system 100 potentially may resultin improved memory utilization, a reduced number of required reclaimoperations, and data preservation.

FIG. 2 illustrates one embodiment of a memory 200. The memory 200 maycomprise a non-volatile memory buffer 202 including a first non-volatilememory region 204-1 and a second non-volatile memory region 204-2. Thememory 200 also may comprise a separate storage location 206 and anallocation table 208. The memory 200 may be implemented by non-volatilememory, such as NOR or NAND flash memory. In various embodiments, thememory 200 may comprise or be implemented as the memory 108 of FIG. 1.The embodiments, however, are not limited in this context.

As shown in FIG. 2, the contents of the non-volatile memory buffer 202including data files (Data1 . . . Data8) have been copied from the firstnon-volatile memory region 204-1 and the second non-volatile memoryregion 204-2 to the separate storage location 206. In variousembodiments, the separate storage location 206 may comprise a morepermanent storage location, such as a write-restricted non-volatilememory region (e.g., object mode non-volatile memory region). In thisexample, the data files (Data1 . . . Data8) may comprise small dataitems having an aggregate size of less than or equal to the storagecapacity (e.g., 1 KB) of the separate storage location 206. It can beappreciated that, in various implementations, the contents of thenon-volatile memory buffer 202 may be written to the separate memorylocation 206 in full storage region granularity.

The allocation table 208 may comprise, for example, a data structurestoring header information pointing to the locations of the data files(Data1 . . . Data8) in the storage location 206. In various embodiments,the allocation table 208 may comprise a rewritable non-volatile memoryregion (e.g., control mode non-volatile memory region) configured tosupport storing the dynamic header information.

In various embodiments, the non-volatile memory buffer 202 may be markedfor reclaim. Marking or initiating a process on the non-volatile memorybuffer 202 for reclaim may result in operations to retrieve free spacefrom dirty space. The reclaim operations may comprise, for example,copying or moving the contents of the non-volatile memory buffer 202 tothe separate memory location 206 and then erasing the non-volatilememory buffer 202 to reclaim free space. The non-volatile memory buffer202 may have been marked for reclaim after meeting a certain datacapacity threshold, for example. The reclaim operations may be triggeredwhen the amount of dirty space exceeds a certain amount of thenon-volatile memory buffer (background reclaim) and/or when one or moreadditional memory regions are allocated (foreground reclaim).

In various implementations, the memory 200 potentially may result in areduced number of required reclaim operations. As shown in FIG. 2, forexample, after copying the contents to the separate memory location 206,only the first non-volatile memory region 204-1 and the secondnon-volatile memory region 204-2 must be erased to reclaim free space.

FIG. 3 illustrates one embodiment of a memory 300. In variousembodiments, the memory 300 may comprise a multi-partition, symmetricalarchitecture and may be implemented as the memory of FIG. 1 and/or thememory 200 of FIG. 2. The embodiments, however, are not limited in thiscontext.

As shown, the memory 300 may comprise a non-volatile memory array 302,such as a flash memory array. In one embodiment, the non-volatile memoryarray 302 may be divided into multiple partitions, such as partitions304-1-8. Although a limited number of partitions (e.g., eightpartitions) are shown by way of example, it can be appreciated that moreor fewer partitions may be used for a given implementation.

In various embodiments, each of the partitions 304-1-8 may be dividedinto multiple non-volatile memory blocks, such as flash memory blocks.As shown, the partition 304-1 may comprise non-volatile memory blocks306-1-n, where n represents a positive integer value. In one embodiment,each of the non-volatile memory blocks may comprise 256 KB. Whenimplemented by a 256-Mb device, for example, each of the partitions304-1-8 may comprise non-volatile memory blocks 306-1-16 (n=16), and thenon-volatile memory array 302 may comprise 128 non-volatile memoryblocks. When implemented by a 512-Mb device, for example, each of thepartitions 304-1-8 may comprise non-volatile memory blocks 306-1-32(n=32), and the non-volatile memory array 302 may comprise 256non-volatile memory blocks.

In various embodiments, each non-volatile memory block 306-1-n may beorganized by programming regions and segments. As shown, thenon-volatile memory block 306-1 may comprise programming regions308-1-p, and the programming region 308-1 may comprise segments 310-1-s, where p and s represent positive integer values. In one embodiment,for example, each of the non-volatile memory blocks 306-1-n may comprise256 KB and may include programming regions 308-1-256 (p=256). Each ofthe programming regions 308-1-p may comprise 1 KB (1 KB=1024 bytes=512words) and may include segments 310-1-32 (s=32). Each of the segments310-1-s may comprise 32 bytes (16 words) and may be divided into twohalves. For example, the segment 310-1 may be divided into A-half 301 -1-a and B-half 310-1 -b.

In various embodiments, each of the programming regions 308-1 -p may beprogrammed in multiple modes, such as a control mode and an object mode.When control mode programming is used, the A-half of a programmingregion may be programmed to 0s and the B-half may remain erased. Invarious implementations, control mode programming may allow up to 512bytes of data to be programmed in bits, bytes, or words into aprogramming region. When object mode programming is used, one or morebits are programmed to zero in the B-half of a programming region. Invarious implementations, object mode programming may allow up to 1 KB ofdata to be stored in a programming region. Multiple regions may be usedto store more than 1 KB of data.

FIG. 4 illustrates one embodiment of a data storage manager 400. Invarious embodiments, the data storage manager 400 may comprise or beimplemented as the data storage manager 102 of FIG. 1. The embodiments,however, are not limited in this context.

As shown, the data storage manager 400 may comprise a file managermodule 402, a media file manager core module 404, a memory interfacemodule 406, and a memory driver module 408. The modules may comprise orbe implemented as one or more systems, sub-systems, processors, devices,machines, tools, components, circuits, registers, applications,programs, subroutines, or any combination thereof, as desired for agiven set of design or performance constraints.

In various implementations, the file manager module 402 may be arrangedto provide a programming interface for a client applications and/or anoperating system, such as RTOS. In various embodiments, the file managermodule 402 may comprise application programming interfaces (APIs) tointerface client applications and RTOS file calls. The API functions mayallow client applications and RTOS applications to interface with themedia file manager core module 404 through the file manager module 402.

In various implementations, the media file manager core module 404 maybe arranged to manage and store media information to be stored in amemory device (e.g., NOR or NAND flash memory device). The mediainformation may comprise media files and/or data files that are requiredto be immediately stored, instantly transmitted, updated and/or edited.Examples of media files to be stored in flash memory include: imagefiles (e.g., digital photographs), audio files (e.g., music files, soundfiles), and so forth that might require editing. Exampled of data filesto be stored in flash memory include: system files, text messaging,e-mail messages, contact lists, task lists, calendar entries, and soforth that might require immediate storage and/or frequent updating(e.g., addition of new data, deletion of obsolete data).

In various implementations, the memory interface module 406 may bearranged to enable the media file manager core module 404 to communicatethrough the memory driver module 408 to the memory device. In variousembodiments, the functions of the memory interface module 406 may calldown into the platform-specific functions of the memory driver module408. The memory interface module 406 may be arranged to issue read,write, and erase commands for the memory device and to translate filesystem volumes into memory arrays.

In various implementations, the memory driver module 408 may be arrangedto interface the media file manager core module 404 module to the memorydevice. In various embodiments, the memory driver module 408 may beresponsible for directly manipulating the memory hardware of the memorydevice.

Operations for various embodiments may be further described withreference to the following figures and accompanying examples. Some ofthe figures may include a logic flow. It can be appreciated that thelogic flow merely provides one example of how the described fuctionalitymay be implemented. Further, the given logic flow does not necessarilyhave to be executed in the order presented unless otherwise indicated.In addition, the logic flow may be implemented by a hardware element, asoftware element executed by a processor, or any combination thereof.The embodiments are not limited in this context.

FIG. 5 illustrates one embodiment of a logic flow 500. FIG. 5illustrates logic flow 500 for non-volatile memory buffering. In variousembodiments, the logic flow 500 may be implemented by a system (e.g.,memory system 100), a memory (e.g., memory 200, memory 300), and/or adata storage manager (e.g., data storage manager 400). It can beappreciated that the logic flow 500 may be implemented by various othertypes of hardware, software, and/or combination thereof.

In various embodiments, the logic flow 500 may comprise a start filewrite (block 502). In various implementations, the start file write maybe initiated by a data storage manager in response to a RTOS or clientapplication, for example.

In various embodiments, the logic flow 500 may comprise a file objectwrite request API call (block 504). In various implementations, the fileobject write request API call may be received and handled by a datastorage manager.

In various embodiments, the logic flow 500 may comprise determiningwhether the file size of the data item is less than or equal to athreshold value (block 506). In various implementations, the file sizeof the data item may be determined and compared to the threshold value.The threshold value generally may be used to determine if file size ofthe data item fits a target size for storage in a non-volatile memorybuffer. The threshold value may comprise or be based on a data storagecapacity (e.g., 512 bytes) of the non-volatile memory buffer. In somecases, the threshold value may be a predefined and/or set value. Inother cases, the threshold may be a floating and/or configurable value.

In various embodiments, if the file size of the data item is not lessthan or equal to the threshold value, the logic flow 500 may compriseperforming a standard file handling write process (block 508). Invarious implementations, standard file handling and write processing maycomprise, for example, storing the data item in a write-restrictedmemory region of flash memory, such as an object mode non-volatilememory region.

In various embodiments, if the file size of the data item is less thanor equal to the threshold value, the logic flow 500 may comprisedetermining whether a non-volatile memory buffer exists (block 510). Invarious implementations, the data item may be stored in a non-volatilememory buffer if the data item comprises a small data item having a filesize less than or equal to the threshold value.

In various embodiments, if a non-volatile memory buffer does not exist,the logic flow 500 may comprise allocating a non-volatile memory buffer(block 512). In various implementations, the non-volatile memory buffermay be allocated on-the-fly and may comprise floating memory regions inflash memory. In other cases, the non-volatile memory buffer may bepre-allocated within the flash memory.

In various embodiments, the non-volatile memory buffer may comprise arewritable non-volatile memory buffer including one or more rewritablenon-volatile memory regions. A non-volatile memory region may comprisethe smallest write structure supported by the flash memory. In variousimplementations, the non-volatile memory buffer may be allocated byprogramming the non-volatile memory regions. In some implementations,each of the non-volatile memory regions may be configured to berewritable and to support multiple programming operations for storingone or more small data items. In some implementations, each of thenon-volatile memory regions may be configured to have a data storagecapacity comprising only a portion (e.g., half) of a full data storagecapacity for a non-volatile memory region.

In various embodiments, the logic flow 500 may comprise determiningwhether the file size of the data item is less than or equal to freespace in the non-volatile memory buffer (block 514). In variousimplementations, the free space in the non-volatile memory buffer maycomprise the available storage capacity of one or more non-volatilememory regions.

In various embodiments, if the file size of the data item is greaterthan the free space in the non-volatile memory buffer, the logic flow500 may comprise marking or initiating a process on the non-volatilememory buffer for reclaim (block 516) and allocating one or moreadditional non-volatile memory regions (block 518). The additionalallocated non-volatile memory regions may comprise, for example, anannex to the non-volatile memory buffer and/or a new non-volatile memorybuffer. Marking the non-volatile memory buffer for reclaim may result insubsequent operations to retrieve free space from dirty space. Reclaimoperations may comprise, for example, copying or moving the data storedin the non-volatile memory buffer to a separate memory location and thenerasing the non-volatile memory buffer to reclaim free space. Thereclaim operations may be triggered when the amount of dirty spaceexceeds a certain amount of the non-volatile memory buffer (backgroundreclaim) and/or when one or more additional memory region are allocated(foreground reclaim).

In various embodiments, if the file size of the data item is less thanor equal to the available free space in the non-volatile memory buffer,the logic flow 500 may comprising writing the data item to thenon-volatile memory buffer (block 520). Writing the data item to thenon-volatile memory buffer may comprise, for example, writing,rewriting, augmenting, altering, changing, and/or updating thenon-volatile memory buffer. In various implementations, the data itemmay be written to a rewritable non-volatile memory region of the memorybuffer.

In various embodiments, the logic flow 500 may comprise determiningwhether the non-volatile memory buffer has been filled past a certaindata capacity threshold (block 522). In various implementations, thedetermination may be made after the data item has been stored in thenon-volatile memory buffer.

In various embodiments, if the non-volatile memory buffer has beenfilled past a certain data capacity threshold, the logic flow 500 maycomprise marking the non-volatile memory for reclaim (block 524).Otherwise, one or more additional small data items potentially may bestored in the non-volatile memory buffer.

In various embodiments, after the non-volatile memory buffer is markedor processed for reclaim, the logic flow 500 may comprise performing awrite complete (block 526). In various embodiments, the write completemay comprise moving the contents of the non-volatile memory buffer to aseparate or more permanent memory location, such as a write-restrictednon-volatile memory region. The contents of the non-volatile memorybuffer may comprise, for example, one or more small data items. Invarious implementations, the contents of the non-volatile memory buffermay be written to the separate memory location in full storage regiongranularity.

In various implementations, the logic flow 500 potentially may result inimproved memory utilization, a reduced number of required reclaimoperations, and data preservation.

Numerous specific details have been set forth herein to provide athorough understanding of the embodiments. It will be understood bythose skilled in the art, however, that the embodiments may be practicedwithout these specific details. In other instances, well-knownoperations, components and circuits have not been described in detail soas not to obscure the embodiments. It can be appreciated that thespecific structural and functional details disclosed herein may berepresentative and do not necessarily limit the scope of theembodiments.

In various implementations, the described embodiments may comprise, orform part of a wired communication system, a wireless communicationsystem, or a combination of both. Although certain embodiments may beillustrated using a particular communications media by way of example,it may be appreciated that the principles and techniques discussedherein may be implemented using various communication media andaccompanying technology.

In various implementations, the described embodiments may comprise orform part of a network, such as a Wide Area Network (WAN), a Local AreaNetwork (LAN), a Metropolitan Area Network (MAN), a wireless WAN (WWAN),a wireless LAN (WLAN), a wireless MAN (WMAN), a wireless personal areanetwork (WPAN), a WiMAX network, a broadband wireless access (BWA)network, the Internet, the World Wide Web, a telephone network, a radionetwork, a television network, a cable network, a satellite network, aCode Division Multiple Access (CDMA) network, a third generation (3G)network such as Wide-band CDMA (WCDMA), a fourth generation (4G)network, a Time Division Multiple Access (TDMA) network, anExtended-TDMA (E-TDMA) cellular radiotelephone network, a Global Systemfor Mobile Communications (GSM) network, a Synchronous Division MultipleAccess (SDMA) network, a Time Division Synchronous CDMA (TD-SCDMA)network, an Orthogonal Frequency Division Multiplexing (OFDM) network,an Orthogonal Frequency Division Multiple Access (OFDMA) network, aNorth American Digital Cellular (NADC) cellular radiotelephone network,a Narrowband Advanced Mobile Phone Service (NAMPS) network, a UniversalMobile Telephone System (UMTS) network, and/or any other wired orwireless communications network configured to carry data. Theembodiments are not limited in this context.

In various implementations, the described embodiments may employ one ormore protocols such as medium access control (MAC) protocol, PhysicalLayer Convergence Protocol (PLCP), Simple Network Management Protocol(SNMP), Asynchronous Transfer Mode (ATM) protocol, Frame Relay protocol,Systems Network Architecture (SNA) protocol, Transport Control Protocol(TCP), Internet Protocol (IP), TCP/IP, X.25, Hypertext Transfer Protocol(HTTP), User Datagram Protocol (UDP), and so forth.

In various implementations, the described embodiments may be arranged tocommunicate in accordance with a number of wireless protocols. Examplesof wireless protocols may include various wireless local area network(WLAN) protocols, including the Institute of Electrical and ElectronicsEngineers (IEEE) 802.xx series of protocols, such as IEEE 802.11a/b/g/n,IEEE 802.16, IEEE 802.20, and so forth. Other examples of wirelessprotocols may include various WWAN protocols, such as GSM cellularradiotelephone system protocols with GPRS, CDMA cellular radiotelephonecommunication systems with 1×RTT, EDGE systems, EV-DO systems, EV-DVsystems, HSDPA systems, and so forth. Further examples of wirelessprotocols may include WPAN protocols, such as an Infrared protocol, aprotocol from the Bluetooth Special Interest Group (SIG) series ofprotocols, including Bluetooth Specification versions v1.0, v1.1, v1.2,v2.0, v2.0 with Enhanced Data Rate (EDR), as well as one or moreBluetooth Profiles, and so forth. Yet another example of wirelessprotocols may include near-field communication techniques and protocols,such as electromagnetic induction (EMI) techniques. An example of EMItechniques may include passive or active radio-frequency identification(RFID) protocols and devices. Other suitable protocols may include UltraWide Band (UWB), Digital Office (DO), Digital Home, Trusted PlatformModule (TPM), ZigBee, and other protocols. The embodiments are notlimited in this context.

In various implementations, the described embodiments may be arranged tocommunicate using a number of different WWAN data communicationservices. Examples of cellular data communication systems offering WWANdata communication services may include a GSM with General Packet RadioService (GPRS) systems (GSM/GPRS), CDMA/1×RTT systems, Enhanced DataRates for Global Evolution (EDGE) systems, Evolution Data Only orEvolution Data Optimized (EV-DO) systems, Evolution For Data and Voice(EV-DV) systems, High Speed Downlink Packet Access (HSDPA) systems, andso forth. The embodiments are not limited in this respect.

In various embodiments, communications media may be connected to anetwork element using an input/output (I/O) adapter. The I/O adapter maybe arranged to operate with any suitable technique for controllinginformation signals using a desired set of communications protocols,services or operating procedures. The I/O adapter may also include theappropriate physical connectors to connect the I/O adapter with acorresponding communications medium. Examples of an I/O adapter mayinclude a network interface, a network interface card (NIC), disccontroller, video controller, audio controller, and so forth. Theembodiments are not limited in this context.

Unless specifically stated otherwise, it may be appreciated that termssuch as “processing,” “computing,” “calculating,” “determining,” or thelike, refer to the action and/or processes of a computer or computingsystem, or similar electronic computing device, that manipulates and/ortransforms data represented as physical quantities (e.g., electronic)within the computing system's registers and/or memories into other datasimilarly represented as physical quantities within the computingsystem's memories, registers or other such information storage,transmission or display devices. The embodiments are not limited in thiscontext.

Some embodiments may be implemented, for example, using amachine-readable medium or article which may store an instruction or aset of instructions that, if executed by a machine, may cause themachine to perform a method and/or operations in accordance with theembodiments. Such a machine may include, for example, any suitableprocessing platform, computing platform, computing device, processingdevice, computing system, processing system, computer, processor, or thelike, and may be implemented using any suitable combination of hardwareand/or software. The machine-readable medium or article may include, forexample, any suitable type of memory unit, memory device, memoryarticle, memory medium, storage device, storage article, storage mediumand/or storage unit, for example, memory, removable or non-removablemedia, erasable or non-erasable media, writeable or re-writeable media,digital or analog media, hard disk, floppy disk, Compact Disk Read OnlyMemory (CD-ROM), Compact Disk Recordable (CD-R), Compact DiskRewriteable (CD-RW), optical disk, magnetic media, magneto-opticalmedia, removable memory cards or disks, various types of DigitalVersatile Disk (DVD), a tape, a cassette, or the like. The instructionsmay include any suitable type of code, such as source code, compiledcode, interpreted code, executable code, static code, dynamic code, andthe like. The instructions may be implemented using any suitablehigh-level, low-level, object-oriented, visual, compiled and/orinterpreted programming language, such as C, C++, Java, BASIC, Perl,Matlab, Pascal, Visual BASIC, assembly language, machine code, and soforth. The embodiments are not limited in this context.

Some embodiments may be implemented using an architecture that may varyin accordance with any number of factors, such as desired computationalrate, power levels, heat tolerances, processing cycle budget, input datarates, output data rates, memory resources, data bus speeds and otherperformance constraints. For example, an embodiment may be implementedusing software executed by a general-purpose or special-purposeprocessor. In another example, an embodiment may be implemented asdedicated hardware, such as a circuit, an ASIC, PLD or DSP, and soforth. In yet another example, an embodiment may be implemented by anycombination of programmed general-purpose computer components and customhardware components. The embodiments are not limited in this context.

It is also worthy to note that any reference to “one embodiment” or “anembodiment” means that a particular feature, structure, orcharacteristic described in connection with the embodiment is includedin at least one embodiment. The appearances of the phrase “in oneembodiment” in various places in the specification are not necessarilyall referring to the same embodiment.

While certain features of the embodiments have been illustrated asdescribed herein, many modifications, substitutions, changes andequivalents will now occur to those skilled in the art. It is thereforeto be understood that the appended claims are intended to cover all suchmodifications and changes as fall within the true spirit of theembodiments.

1. An apparatus comprising: a data storage manager to store a data itemin a non-volatile memory buffer, said data item comprising a file sizeless than or equal to a threshold value, said non-volatile memory buffercomprising a rewritable non-volatile memory buffer including one or morerewritable memory regions configured to store said data item.
 2. Theapparatus of claim 1, said data storage manager to store multiple dataitems in said non-volatile memory buffer.
 3. The apparatus of claim 1,said data storage manager to mark said non-volatile memory buffer toreclaim free space when a data capacity threshold of said non-volatilememory buffer has been met.
 4. The apparatus of claim 1, said datastorage manager to copy contents of said non-volatile memory buffer to aseparate memory location.
 5. The apparatus of claim 1, furthercomprising a non-volatile memory to implement said non-volatile memorybuffer.
 6. A system comprising: an operating system; and a data storagemanager to integrate with said operating system, said data storagemanager to store a data item in a non-volatile memory buffer, said dataitem comprising a file size less than or equal to a threshold value,said non-volatile memory buffer comprising a rewritable non-volatilememory buffer including one or more rewritable memory regions configuredto store said data item.
 7. The system of claim 6, said data storagemanager to store multiple data items in said non-volatile memory buffer.8. The system of claim 6, said data storage manager to mark or initiatea process on said non-volatile memory buffer to reclaim free space whena data capacity threshold of said non-volatile memory buffer has beenmet.
 9. The system of claim 6, said data storage manager to copycontents of said non-volatile memory buffer to a separate memorylocation.
 10. The system of claim 6, further comprising a non-volatilememory to implement said non-volatile memory buffer.
 11. A method,comprising: receiving a data item comprising a file size less than orequal to a threshold value; and storing said data item in a non-volatilememory buffer, said non-volatile memory buffer comprising a rewritablenon-volatile memory buffer including one or more rewritable memoryregions configured to store said data item.
 12. The method of claim 11,further comprising storing multiple data items in said non-volatilememory buffer.
 13. The method of claim 11, further comprising markingsaid non-volatile memory buffer to reclaim free space when a datacapacity threshold of said non-volatile memory buffer has been met. 14.The method of claim 11, further comprising copying contents of saidnon-volatile memory buffer to a separate memory location.
 15. The methodof claim 11, further comprising allocating said non-volatile memorybuffer in non-volatile memory.
 16. An article comprising amachine-readable storage medium containing instructions that if executedenable a system to: receive a data item comprising a file size less thanor equal to a threshold value; and store said data item in anon-volatile memory buffer, said non-volatile memory buffer comprising arewritable non-volatile memory buffer including one or more rewritablememory regions configured to store said data item.
 17. The article ofclaim 16, further comprising instructions that if executed enable asystem to store multiple data items in said non-volatile memory buffer.18. The article of claim 16, further comprising instructions that ifexecuted enable a system to mark or initiate a process on saidnon-volatile memory buffer to reclaim free space when a data capacitythreshold of said non-volatile memory buffer has been met.
 19. Thearticle of claim 16, further comprising instructions that if executedenable a system to copy contents of said non-volatile memory buffer to aseparate memory location.
 20. The article of claim 16, furthercomprising instructions that if executed enable a system to allocatesaid non-volatile memory buffer in non-volatile memory.